Mapping service for local content redirection

ABSTRACT

A mapping service in the mobile core network located after a packet data network gateway examines content requests from user equipment across a first PDN connection to determine if content associated with the content request is cached at an edge server outside of the packet data network. If the content from the packet data network is cached at the edge server, the mapping service redirects the user equipment to request the content from the edge server across a second PDN connection. By using a mapping service located after the packet data network gateway, the content requests may have already passed restrictions such as parental controls.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/315,904, filed Dec. 2, 2016, which is a National Stage ofInternational Application No. PCT/US2015/035297, filed Jun. 11, 2015,which claims the benefit of U.S. Provisional application No. 62/010,692,filed Jun. 11, 2014, the disclosures of which are incorporated herein byreference in their entireties.

BACKGROUND

The 3rd Generation Partnership Project (3GPP) covers cellulartelecommunications network technologies, including radio access, thecore transport network, and service capabilities. The latest version ofthe 3GPP mobile core network (MCN) architecture for wirelesscommunications is referred to as the Evolved Packet Core (EPC). TheEvolved Packet Core (EPC) has a “flat architecture” to handle the datatraffic efficiently from performance and cost perspective. EPC alsoseparates the user data (also known as the user plane) and the signaling(also known as the control plane) to allow the EPC's control and dataplanes to scale independently.

FIG. 1 is a basic architecture diagram illustrating User Equipment (UE)104 (e.g., a mobile phone or other wireless device) connectable to aMobile Core Network (MCN) 102, such as an EPC, and connectable to alocal network 128 through a L-GW 130.

In this diagram, the UE 104 connects to a Small Cell Access Point(SC-AP) 106. Small Cell Access Point (SC-AP) 106 is a low-powered radioaccess node with a range that is small compared to a mobile macrocell.The Small Cell Access Point (SC-AP) 106 can be designed for deploymentin small coverage areas such as indoors or for small public hotspots.Small cells include femtocells having a range on the order of 10 meters.In 3GPP, SC-APs include a Home Node B (HNB), which is a 3G femtocell,and a Home eNode B (HeNB), which is an LTE (Long Term Evolution)femtocell.

Security Gateway (SeGW) 108 is shown in the MCN 102. The SecurityGateway 108 establishes an IPsec tunnel 110 with the SC-AP 106. InternetProtocol Security (IPsec) is a protocol suite for securing InternetProtocol (IP) communications by authenticating and encrypting each IPpacket of a communication session. In tunnel mode, IPsec encrypts theentire IP packet including headers. These encrypted IP packets are thenencapsulated into new IP packets with new IP headers. The IPsec tunnel110 passes through the backhaul 124 which includes intermediate networklinks between the SC-AP 106 and MCN 102.

The Small Cell Gateway (SC-GW) 112 aggregates traffic from multipleSmall Cell Access Points, including SC-AP 106, into the MCN 102. In FIG.1, the SC-AP 106 is connected using an S1 User (S1-U) interface to theSC-GW 112.

Serving Gateway (S-GW) 114 and Packet Data Network Gateway (PDN-GW) 116deal with the user plane. They transport IP data traffic between theUser Equipment (UE) 104 and external networks, such as Packet DataNetwork (PDN) 118. The Serving GW 114 is the point of interconnect onthe radio side. In this case, the S-GW 114 is connected through theSC-GW 112. Serving Gateway 114 serves the UE 104 by routing incoming andoutgoing IP packets. The S-GW 114 is connected to the PDN GW 116.

The PDN GW 116 is the point of interconnect between the MCN 102 andexternal networks PDN 118. PDN 118 can be an IP network, such as theInternet. The PDN-GW 116 routes packets to and from PDNs, such as PDN118.

The MME (Mobility Management Entity) 120 deals with the control plane.It handles the signaling related to mobility and security. The MME 120is responsible for the tracking and the paging of UEs in idle-mode. Itis also the termination point of the Non-Access Stratum (NAS) messaging.

The HSS (Home Subscriber Server) 122 is a database that containsuser-related and subscriber-related information. It also providessupport functions in mobility management, call and session setup, userauthentication and access authorization.

The Policy and Charging Rules Function (PCRF) 126 determines policyrules of the network in real time. The PCRF 126 accesses subscriberdatabases and other specialized functions, such as a charging system, ina centralized manner.

The MCN 102, such as an EPC, can provide Quality of Service (QoS) tousers who access content over the Packet Data Network (PDN) 118, such asthe Internet. The PDN connection of UE 104 through the MCN 102 can beconfigured to provide various levels of QoS.

The SC-AP 106 also has the capacity to connect to a local network 128through a Local Gateway (L-GW) 130. In this way, the User Equipment 104can use resources at the local network 128, such as office printers,without routing through the MCN 102. The L-GW 130 can be integrated withthe SC-AP 106 or be a standalone box.

In R12 of 3GPP, the E-UTRAN/EPC architecture includes a feature calledSelected Internet IP Traffic Offload at the Local Network (SIPTO@LN).SIPTO@LN can be used to allow the UE to 104 connect through an L-GW 130to the Internet. The SIPTO@LN feature allows the MME 120 to direct theUE 104 to break a PDN connection that is currently anchored to P-GW 116in the MCN 102 and establish a new PDN connection that is anchored tothe L-GW 130. The new PDN connection with the L-GW 130 can then be usedby the UE 104 to access the Internet. The traffic from the UE 104 isthus offloaded from the backhaul 124 and MCN 102.

Edge caching is discussed in the Small Cell Forum's document SCF088. Oneexample use case describes an Small Cell Network (SCN) deployed in ashopping mall. The SCN offers caching services to content providers. Thecontent provider may offer web accessible advertisements, videos, webpages, etc. The content provider is able to cache content in the SCN,thus providing more efficient (lower latency) access to the user andoffloading traffic from the back haul and mobile core network.

In the Small Cell Forum's document SCF088, the Small Cell Forum createda basic architecture framework for supporting edge caching. Theframework is shown in FIG. 2.

The architecture of FIG. 2 shows that the caching service consists offour main components—the Edge Server(s) 202, the Local Mapping Service204, the Management Portal 206 and the Local Data Collection andAnalytics Service 208. The edge server(s) 202 are used to store cachedcontent. The local mapping service 204 checks if requests from the UE210 are available in the local edge server 202 and directs the UE 210 tothe cached content. The local mapping service 204 may explicitlyredirect the UE 210 to the cached content or transparently forward theUE's request to the edge server 202. In other words, when explicitmethods of redirection are used, the UE 210 is aware that it isaccessing cached content and when transparent methods of redirection areused, the UE 210 is not aware that it is accessing cached content.

The management portal 206 is used by content providers to loadcontent/data into the edge server(s) 202 of the small cell network.Content placement methods may be transparent or explicit/directed. Anexplicit method of loading content would be when a content providerintentionally loads content into the edge server for future retrieval.Transparent methods are used when the network autonomously decides tocreate a cached copy of some remote content.

The management portal 206 may also be used to access the local datacollection and analytics service 208. The local data collection andanalytics service 208 can be used by the original content provider tomanage any content that is cached in the edge servers 202 and to viewanalytics, or statistics, about how such content is accessed.

With the foregoing as background information, the present applicationdiscloses a new method and system for caching content in a mobile corenetwork.

SUMMARY

Embodiments use a mapping service placed in the EPC after the P-GW. Whencontent is loaded into edge servers, the mapping service can be updatedwith information about what content is available at the edge servers andcan be provided with the local IP address or URI of the cached content.The mapping can use an explicit mapping strategy.

By locating the mapping/redirection function after the P-GW, thearchitecture allows for access policies, such as parental controls, tobe enforced by the Mobile Network Operator (MNO). For example, all ofthe content requests from a UE can be filtered for access policiesbefore these content requests reach the mapping service.

Embodiments also account for the user mobility issues that arise whenthe user roams into and out of the local network.

In one embodiment, when the UE connects to a small cell access pointthat can access an L-GW or Local Home Network (LHN) that has access toedge servers, the opportunity to access cached content is detected bythe MME. The MME can use a new NAS mobility management message torequest that the UE initiate a second PDN connection with the localnetwork. The second PDN connection can be simultaneously maintained withthe UE's first PDN connection. The mapping service is allowed toredirect the UE to the second PDN connection when cached content isavailable. By using a second PDN connection to take advantage of cachingopportunities, the user is able to seamlessly transition between asingle PDN connection and a dual PDN connection as the UE moves in andout of the local network.

APN-Configuration updates can be used so that the MME is aware of theavailability of the edge servers at local networks behind L-GWs.

An alternative architecture can be used where the edge servers reside ina regular (non-local) PDN that is owned by the MNO. The advantage ofthis architecture is that cached content can be placed in a PDN that isaccessible via dedicated P-GW(s), thus offloading P-GW(s) and other EPCnodes that service of other PDN's such as the public internet.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a basic architecture diagram illustrating User Equipmentconnectable to a Mobile Core Network and to a local network.

FIG. 2 is a basic architecture diagram illustrating a caching servicewith a local mapping service.

FIG. 3 is a basic architecture diagram illustrating an explicit mappingstrategy of one embodiment with a Mapping Service located in the MobileCore Network after the P-GW.

FIG. 4 is a diagram that illustrates loading content into edge serversin one embodiment.

FIG. 5 is a diagram that illustrates a call flow in one where the UE isdirected to connect to the L-GW.

FIG. 6 is a diagram that illustrates an UE retrieving content from anoriginal content server as a result of an initial HTTP request and beingredirected to content in an edge server in response to a second request.

FIG. 7 is a diagram that illustrates to ending a PDN connection when aUE moves to an SC-AP that does not have access to a L-GW.

FIG. 8 is a diagram that illustrates an embodiment with a MappingService located in the Mobile Core Network after the P-GW and anadditional local Mapping Service in the local network.

FIG. 9 is a diagram that illustrates an embodiment with a MappingService located in the Mobile Core Network after the P-GW and a specialPDN that holds the edge servers.

FIG. 10 is a diagram of an example end node, such as an UE.

FIG. 11 and FIG. 12 show a block diagram of a computer system or serverthat may be used to implement any of the core network nodes or endpoints illustrated in FIGS. 3-9, including any node on which a MappingService may be implemented.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

FIG. 3 is a basic architecture diagram illustrating an explicit mappingstrategy of one embodiment with a Mapping Service 302 located in theMobile Core Network 102 after the P-GW 116. UE 104 has a connection tothe PDN 118 via an SC-AP 106, Backhaul 124, and Mobile Core Network(MCN) 102. If the UE 104 has no connection to an L-GW 130 and a localnetwork 128, then the Mapping Service 302 in FIG. 3 may be considered“transparent”. In other words, if there is no local connection, thencontent is retrieved from the PDN 118. When the UE 104 has a connectionto the L-GW 130, it may retrieve cached content from the edge servers308.

In this embodiment, the UE maintains two simultaneous PDN connections304 and 306. The second PDN connection 306 is used for retrieving cachedcontent. The UE 104 is explicitly directed to the local network 128 bythe mapping service 302.

By placing the mapping service 302 after the P-GW 116, the architectureallows for restrictions, such as parental controls, to be applied to UE104 content requests before decisions are made about redirecting therequest.

Before the UE 104 can retrieve content from the Edge Servers 308, theContent Provider 312 loads the Edge Servers 308 with content and theMapping Service 302 is notified that the cached content is available. UE104 recognizes that there is an L-GW 130 available to the UE 104 thatprovides access to the Edge Servers 308. UE 104 also establishes a PDNconnection with the L-GW 130. The Mapping Service 302 becomes aware thatthe UE 104 can access the edge servers 308. When the Mapping Service 302detects that the UE 104 is accessing content that is available in theEdge Servers 308, the Mapping Service 302 redirects the UE 104 to thecontent in the Edge Server 308. Alternatively, the P-GW 116 may becomeaware that the UE 104 can access the Edge Servers 308. The P-GW 116 maythen mark IP packets that originate from the UE 104 so that the UE's 104traffic may be steered to the Mapping Service 302. The P-GW 116 may benotified by the PCRF 126 when the UE 104 has access to edge servers 308and UE 104 traffic should be redirected, or steered, towards the mappingservice.

If the UE 104 moves to a Small Cell that cannot reach the L-GW 130, theUE 104 disconnects its PDN connection with the L-GW 116 and the MappingService 302 or P-GW 116 become aware that it can no longer redirect theUE 104.

In one embodiment, the Mobile Network Operator (MNO) can own, operate,and/or have a business relationship with the host of the Edge Servers308 and Mapping Service 302.

In the example of FIG. 3, a management portal 310 is available tocontent providers 312. The management portal 310 allows contentproviders 312 to load content into the edge servers 308 and update themapping service 302 accordingly. In other words, when content is loadedinto the edge servers 308, the management portal 310 notifies themapping service 302 so that the mapping service 302 is aware of whatcontent is available in each local network. For example, a contentprovider 312 may want to cache the content of a popular web page calledexample.com/example-page. The content provider 312 uses the managementportal 310 to send the content of example.com/example-page to the edgeservers 308. The management portal 310 notifies the mapping service 302that a cached copy of example.com/example-page is available in the localnetwork 128. The management portal 310 can connect to the edge servers308 (and data collection and analytics 314) using PDN network 316.

It is understood that the functionality illustrated in FIG. 3, may beimplemented in the form of software (i.e., computer-executableinstructions) stored in a memory of, and executing on a processor of, anode of an M2M network (e.g., a server, gateway, device, or othercomputer system), such as one of those illustrated in FIG. 11 or 12described below.

FIG. 4 is a diagram that illustrates loading content into edge servers308 in one embodiment. The example of FIG. 4 has four steps.

In step 1 of FIG. 4, the content provider 312 sends content to themanagement portal 310. This message can include the following fields:

-   -   URL of the original content 314    -   A copy of the original content.    -   The name of the local Access Point Name (APN), L-GW, or LHN-ID,        where the content should be cached. An APN identifies a packet        data network (PDN). The local APN identifies local network 128        with the edge servers 308.    -   Name of the APN(s) that should be associated with this content.        This APN identifies PDN 118 that stores the original content        314.

In step 2 of FIG. 4, the management portal 310 sends the content to theedge servers 308 of the local APN(s) that were indicated in step 1.

In step 3 of FIG. 4, the Edge Server 308 responds with a URL of wherethe cached content can be retrieved.

In step 4 of FIG. 4, the Management Portal 310 sends a notification tothe Mapping Server 302 so that it is aware that the cached content isavailable in a local network 128. This message includes the followingfields:

-   -   URL of the original content 314    -   URL of the cached content and the local IP Address of the Edge        Server.    -   The name of the local APN, L-GW, or LHN-ID, where the content        should be cached.    -   Name of the APN(s) that should be associated with this content.

When the UE 104 performs a Tracking Area Update (TAU), The TRACKING AREAUPDATE REQUEST message to the MME 120 may include a “SIPTO L-GWTransport layer Address” information element or an “LHN-ID” value. TheLHN-ID can be provided to MME 120 by the SC-AP 106, such as by a (H)eNB,in every INITIAL UE MESSAGE and every UPLINK NAS TRANSPORT message. Thepresence of either of these values indicates to the MME 120 that theSC-AP 106 is able to access the L-GW 130.

The MME 120 can determine that the L-GW 130 can access edge servers 308that hold cached content for a particular APN in different ways. The MME120 may be provisioned with a list or have access to a database/listthat enumerates L-GW's and LHN's that are able to access edge serversand what APN's the edge servers can service. Alternately, thesubscribers APN-Configuration can indicate what LHN-ID's and/or L-GW'smay be used to access edge servers that are associated with the APN.

The SC-AP 106 may include the public and local IP address(es) of theedge servers 308 via extensions to the INITIAL UE MESSAGE and UPLINK NASTRANSPORT message. The MME 120 may use the public IP address(es) todetermine what local content the UE 104 is able to access and it may useprivate IP address(es) when redirecting the UE 104.

Thus, when the UE 104 performs the TAU, the MME 120 may detect that theUE 104 is using a Small Cell that has access to an L-GW 130 that canreach edge servers 308 that store cached content. The MME 120 thenfurther checks if the UE's capabilities support connecting to the L-GW130 and if the UE's current APN connection(s) allow for accessing cachedcontent. If the UE 104 is capable, and permitted, to access the cachedcontent, then the MME 120 commands the UE 104 to establish a connectionwith the L-GW 130 that can access the edge servers 308.

When the UE 104 receives the new command from the MME 120, itestablishes a second PDN connection 306 which it maintainssimultaneously with its primary PDN connection 304, which is anchored tothe P-GW 116.

The idea of allowing the MME 120 to command the UE 104 to establish aPDN connection is a new concept. In LTE, there is no concept of anetwork activated PDN connection.

There is an existing procedure whereby the MME 120 may command the UE104 to perform an “explicit detach with reattach required”. Thisprocedure is used when the UE 104 has a SIPTO@LN connection and the UE104 moves to another SC-AP, such as a H(e)NB, that cannot access theL-GW 130 to which the UE 104 is currently attached. The “explicit detachwith reattach required” procedure can be used to command the UE 104 todetach from the L-GW 130 and reattach. When the UE 104 reattaches, theMME 120 selects a P-GW 116 in the MCN 120 for the UE 104.

Embodiments include a modified procedure where the MME 120 detects thatthe UE 104 has moved to a SC-AP 106 that has access to an L-GW 130 thatprovides locally cached content. The MME 120 can send a newNon-Access-Stratum (NAS) message to the UE 104 commanding the UE 104 toestablish a PDN connection 306 with the L-GW 130.

It is understood that the entities performing the steps illustrated inFIG. 4 are logical entities that may be implemented in the form ofsoftware (i.e., computer-executable instructions) stored in a memory of,and executing on a processor of, a network node or computer system suchas those illustrated in FIG. 11 or FIG. 12. That is, the method(s)illustrated in FIG. 4 may be implemented in the form of software (i.e.,computer-executable instructions) stored in a memory of a network node,such as the node or computer system illustrated in FIG. 11 or FIG. 12,which computer executable instructions, when executed by a processor ofthe node, perform the steps illustrated in FIG. 4. It is also understoodthat any transmitting and receiving steps illustrated in FIG. 4 may beperformed by communication circuitry of the node under control of theprocessor of the node and the computer-executable instructions (e.g.,software) that it executes.

FIG. 5 is a diagram that illustrates a call flow in one embodiment wherethe UE 104 is directed to connect to the L-GW 130. This procedure can beused to solve the mobility issue where the UE 104 moves to an SC-AP 106that has access to an L-GW 130 that can access cached content.

Steps labeled 0 a and 0 b of FIG. 5 are preconditions for the method.For precondition 1 (step 0 a) of FIG. 5, The UE 104 Attaches to the MCN102 (EPC). The UE 104 would have used the “E-UTRAN Initial Attach”procedure.

For precondition 2 (step 0 b) of FIG. 5, the UE 104 establishes a PDNconnection 304. The PDN connection 304 is anchored to a P-GW 116 asshown in FIG. 3. The UE 104 would have used the “UE requested PDNconnectivity” procedure to establish this connection.

During the “E-UTRAN Initial Attach” procedure, the MME 120 sends the HSS122 an “Update Location Request” message and the HSS 122 responds withan “Update Location Answer” message. “Update Location Answer” message isused to send the UE's subscription information to the MME 120. Thisexchange occurs on the S6a interface. The HSS 122 is already provisionedwith information about what APN's each UE 104 can connect to. To supportthis new feature, the HSS 122 is provisioned with additional informationfor each subscribed APN that supports caching. The updated informationindicates if an APN supports local caching and what local networks cachedata for the APN. The “Update Location Answer” message carries newinformation to the MME 120 so that the MME 120 knows which of the UE'sAPN's allow PDN content to be cached in some local networks. New fieldsdescribed below are provisioned in the HSS 122 and provided to the MME120 via the S6a interface.

In step 1 of FIG. 5, based on the UE's location, the MME 120 looks foropportunities to direct the UE 104 to establish a local PDN connectionthat can be used to retrieve cached content. The new subscriptioninformation is used by the MME 120 to decide if there is an opportunityto direct the UE 104 to establish a local PDN connection that can beused to retrieve cached content. In the example of FIG. 5, the MME 120(or Mapping Service 302) detects that it is possible for the UE 104 toconnect to a local PDN, Local Network 128, for accessing cached content.

In one alternative labeled step 1 a in FIG. 5, the MME 120 Detects aCache Access Opportunity: During the S1 Application Protocol S1-AP setupprocedure, the SC-AP 106 indicates to the MME 120 that an L-GW 130 isaccessible to the SC-AP 106 and the SC-AP 106 provides to the MME 120the identity of the L-GW 130 or LHN-ID that is accessible to the SC-AP106. The identity is provided in every INITIAL UE MESSAGE and everyUPLINK NAS TRANSPORT message. To support this new feature, the SC-AP 106may indicate to the MME 120 that the L-GW 130 or LHN is cache capableand provide contact information (in the form of an IP address) for itsedge servers. The SC-AP 106 may provide this information to the MME 120as new fields in the INITIAL UE MESSAGE or UPLINK NAS TRANSPORT message.Alternatively, the MME 120 may be provisioned with a list of what L-GW'sor LHN-ID's have access to edge servers 308 and the edge server contactaddresses, or the MME 120 may have access to a database where thisinformation is stored. When a TAU occurs, the MME 120 checks if there isan L-GW 130 that is accessible to the UE 104 for accessing cachedcontent. If a suitable L-GW 130 is available, the MME 120 further checksif the UE's capabilities (which were obtained from the HSS 122 via theS6a interface) support connecting to the L-GW 130.

In another alternative, labeled step 1 b in FIG. 5, the Mapping Service302 detects a cache access opportunity. The Mapping Service 320 or atraffic detection function can detect that the UE 104 is accessing dataor anticipate that the UE 104 will access data that is available in thelocal cache and can send a notification to the MME 120 that a local PDNconnection could be established to access the cache. In this case, themapping service maintains a mapping between the UE's IP address andInternational mobile Subscriber Identity (IMSI) so that the IMSI can beused to identify the UE 104 when the notification is sent to the MME120. For example, the Mapping Service 302 may detect that a UE 104 isaccessing a news article that is similar to some content that isavailable in the edge servers. This could cause the Mapping Service 302to anticipate that the UE 104 may request some content that is availablein the edge servers. The Mapping Service 302 uses the UE's IP Address todetermine (i.e. lookup) the UE's IMSI and send a notification to the MME120. The Notification to the MME 120 indicates that UE 104 (identifiedby an IMSI) could benefit from a PDN connection that provides access tothe edge servers 308. Alternatively, the mapping service 302 maycommunicate with the MME 120 via an inter-working function such as aServices Capability Exposure Function (SCEF). The SCEF may be taskedwith resolving the UE's IP Address to an IMSI and determining what MMEto send the notification to.

In step 2 of FIG. 5, the MME 120 sends a new “PDN SERVICES ADVERTISEMENTREQ” to the UE 104. The “PDN SERVICES ADVERTISEMENT REQ” is a new EPSMobility Management message that that is used to indicate to the UE 104that it should connect to a specific APN in order to access someservice. As described in the previous step, the MME 120 knows to sendthis message because it either detected the cache access opportunity orthe mapping service 302 indicated to the MME 120 that there is a cacheaccess opportunity. In this example, this new message is being used inanticipation of the UE 104 being redirected to some cached content inthe APN. This message can include the following information elements:

-   -   Protocol Discriminator, defined in section 9.2 of the reference,        3GPP TS 24.301, Non-Access-Stratum (NAS) Protocol for Evolved        Packet System (EPS); Stage 3 (Release 12), V12.3.0 (hereafter        “reference 3GPP TS 24.301”)    -   Security Header Type, defined in section 9.3.1 of reference 3GPP        TS 24.301.    -   Message Type, defined in section 9.8 of reference 3GPP TS        24.301. One of the EPC Mobility Management Message Type values,        such as 0x47, can be reserved for the “PDN SERVICES        ADVERTISEMENT REQ” message.    -   A new “Services Advertisement Type” information element can be        used. This information element may be ½ octet in size and it may        indicate what type of services is available in the APN. For        example, a value of 0x01 may indicate that cached content is        accessible in the indicated APN. This field may also useful in        the future if the “PDN SERVICES ADVERTISEMENT REQ” message is        used to direct the UE 104 to a PDN for some reason other than        accessing cached content.    -   Spare half octet, defined in section 9.9.2.9 of reference 3GPP        TS 24.301.    -   Access Point Name, defined in section 9.9.4.1 of reference 3GPP        TS 24.301. The APN name may be a special APN name that is        created by the MME 120 so that when the UE 104 tries to        establish a PDN connection with the APN the MME 120 is able to        easily recognize that the PDN connection should be a with the        detected L-GW 130 or LHN. Alternatively, the PDN SERVICES        ADVERTISEMENT REQ message could indicate the L-GW 130 or LHN-ID        to the UE 104    -   PDN Type, defined in 9.9.4.10 of reference 3GPP TS 24.301.

Additional Information Elements (IE's) may be included to allow help theUE 104 decide if it should connect to the APN. For example, the messagemay include pricing information, or more details about what content isavailable in the APN. Content types may include multimedia,advertisements, web pages, etc. The UE 104 may consider this message tobe a suggestion and choose not to establish local PDN connection thusforgoing the opportunity to access cached content.

In step 3 of FIG. 5, the UE sends a new “PDN SERVICES ADVERTISEMENTRESP” to the MME 120. The “PDN SERVICES ADVERTISEMENT RESP” is a new EPSMobility Management message that that is used to indicate to the MME 120that the UE 104 received the “PDN SERVICES ADVERTISEMENT REQ” message.This message can include the following information elements:

-   -   Protocol Discriminator, defined in section 9.2 of reference 3GPP        TS 24.301.    -   Security Header Type, defined in section 9.3.1 of reference 3GPP        TS 24.301.    -   Message Type, defined in section 9.8 of reference 3GPP TS        24.301. One of the EPC Mobility Management Message Type values,        such as 0x48, can be reserved for the “PDN SERVICES        ADVERTISEMENT RESP” message. Additional IE's may be included to        allow the UE 104 to indicate to the MME 120 if it intends to        connect to the APN.

In step 4 of FIG. 5, the UE 104 executes the “UE requested PDNconnectivity” procedure that is shown in section 5.10.2 of reference,3GPP TS 23.401, General Packet Radio Service (GPRS) enhancements forEvolved Universal Terrestrial Radio Access Network (E-UTRAN) access(Release 12), V12.3.0 (hereinafter “reference 3GPP TS 23.401”) The UE104 executes this procedure because it wants to connect to the local PDNthat holds edge servers and cached content. The UE 104 initiates thisprocedure by sending the “PDN Connectivity Request” message. The “PDNConnectivity Request” indicates that the UE 104 wants to connect to theAPN that was provided to the UE 104 in step 2. The “Request Type” IE ofthe “PDN Connectivity Request” is set to “Initial Request” to indicatethat the request is for a new PDN connection. Alternatively, if the UE104 was provided an L-GW 130 address or LHN-ID by the MME in the “PDNSERVICES ADVERTISEMENT REQ”, the UE 104 could provide that value to theMME 120 in the “PDN Connectivity Request”.

In Step 5 of FIG. 5, the MME 120 knows what PDN connections aremaintained by the UE 104 and when the “UE requested PDN connectivity”procedure is complete, the MME 120 knows that the UE 104 is connected toa local network 128 that can be used to access cached content in theedge servers 308. The MME 120 indicates to the Mapping Service 302 thatthe UE 104 has access to the local APN, L-GW 130, or LHN. Thisindication is sent to the Mapping Service 302 by the MME 120 via a newmessage, SUBSCRIBER LOCAL ACCESS NOTIFICATION, on a new interface. Thenew interface is between the MME 120 and Mapping Service 302. Themapping service 302 has already been provisioned, via the managementportal 310, with information about what content is available in eachlocal APN, L-GW, or in each LHN and the IP Addresses of the edge serverswith the cached content that is available in each local network. Thisnew message can carry the following information:

-   -   Subscription Identifier for the UE, i.e. IMSI    -   APN Name/PDN Connection ID—The name of the APN or PDN Connection        that can be redirected to local access.    -   L-GW Address or LHN-ID—The L-GW or LHN that the UE can use to        retrieve cached content for the indicated APN/PDN Connection.

If the mapping service 302 is not aware of what content is available viathe L-GW 130 that was indicated in the SUBSCRIBER LOCAL ACCESSNOTIFICATION, then the Mapping Service 302 may contact the local networkedge servers 308 and data collection and analytics service 314 to learnabout what content is cached in the local network 128. This may also bewhen the mapping service 302 learns how the public IP addresses oforiginal content map to the local IP addresses the edge servers 308 withcached content. This step can be done if the Mapping Service was notupdated as described above.

The MME 120 could also optionally provide the mapping service 302 withthe public and local IP address(es) of the edge server(s) 308 if thisinformation was provided to the MME 120 by the SC-AP 106.

At the conclusion of this procedure, the UE 104 has two PDN connections;a primary PDN connection 304 that is anchored at the P-GW 116 and asecond PDN connection 306 that is anchored to the L-GW 130. The secondPDN connection 306 that is anchored to the L-GW 130 can be used toaccess cached content in the edge servers 308. The Mapping Service 302is associated with the primary PDN connection 304 and can redirectrequests from the primary PDN connection 304 to the second PDNconnection 306.

When the UE 104 attempts to use its main PDN connection 304 to accesscontent, the mapping service 302 inspects each request and checks if theURL is available in the local network 128 that the UE 104 has access to.If the URL is available, then the mapping service 302 responds to therequest with a redirect response. Alternatively, the message exchange ofsteps 5 and 6 could occur between the MME 120 and P-GW 116 so that theP-GW will receive an indication that the UE 104 has access to the localAPN, L-GW 130, or LHN. The P-GW 116 would then be able to mark packetsfrom the UE 104 so that they can be steered towards the mapping service302.

It is understood that the entities performing the steps illustrated inFIG. 5 are logical entities that may be implemented in the form ofsoftware (i.e., computer-executable instructions) stored in a memory of,and executing on a processor of, a network node or computer system suchas those illustrated in FIG. 11 or FIG. 12. That is, the method(s)illustrated in FIG. 5 may be implemented in the form of software (i.e.,computer-executable instructions) stored in a memory of a network node,such as the node or computer system illustrated in FIG. 11 or FIG. 12,which computer executable instructions, when executed by a processor ofthe node, perform the steps illustrated in FIG. 5. It is also understoodthat any transmitting and receiving steps illustrated in FIG. 4 may beperformed by communication circuitry of the node under control of theprocessor of the node and the computer-executable instructions (e.g.,software) that it executes.

FIG. 6 is a diagram that illustrates an UE 104 retrieving content froman original content server 314 as a result of an initial HTTP request inone embodiment. The UE 104 is then redirected to the local cache 308 asa result of an second HTTP request.

In step 1 of FIG. 6, the UE 104 uses its main PDN Connection to make anHTTP request for some content. The request traverses the Small Cell,P-GW 116, and Mapping Service 302. In the example of step 1 of thisfigure, the mapping service 302 inspects the HTTP request, but findsthat there is no cached copy of the requested content available. Sincethere is no cached content available, the mapping service 302 takes noaction (beyond inspecting the request) and the request is allowed topass to the original content server 314.

In step 2 of FIG. 6, the content server 314 responds with the requestedcontent. The request traverses the Small Cell and P-GW 116. The mappingservice 302 does not inspect downlink packets.

In step 3 of FIG. 6, the UE 104 uses its main PDN Connection to make anHTTP request for some content. The request traverses the Small Cell,P-GW 116, and Mapping Service 302. In step 3 of this figure, the mappingservice inspects the HTTP request and discovers that there is a cachedcopy of the requested content in a Local PDN edge server 308 that the UE104 has access to. Since there is cached content available and the UE104 has access to the local cache, the mapping service 302 redirects theUE 104 to the local content. This is described in the step 4.

In step 4 of FIG. 6, the Mapping Service issues an HTTP RedirectResponse to the UE 104. The redirect response includes the URL of thecached content at the edge servers 308. The URL may include an IPaddress that belongs to the edge server 308 in the local network or aprocedure such as DNS may be used to resolve it to an IP address thatbelongs to the edge server 308 on the local network 128. The mappingservice is after the P-GW 116. Between the P-GW 116 function and MappingService 302, the operator may choose to perform traffic detection andfunctions such as parental controls. If the user is not permitted toretrieve the requested URL, then the request is blocked by the operatorand this request is not be seen by the mapping service.

In step 5 of FIG. 6, the UE 104 uses the URL that was received in theredirect response to again request the content. This time, the UE 104uses its Local PDN connection 306 to make an HTTP request for the cachedcontent at edge server 308. The request traverses the Small Cell andL-GW 130.

In step 6 of FIG. 6, the edge server 308 responds with the requestedcontent. The request traverses the Small Cell and L-GW 130.

The mapping service 302 may use its connection with the managementportal 310 or a connection with the edge servers 308 to obtaininformation about the traffic load in the local network 128 and whatlevel of service can be provided by the local network 128. Thisinformation can be used mapping service 302 when determining if the UE104 should be redirected to the local network 128. The mapping servicemay also have a connection with the PCRF 126 to obtain the QoSrequirements for a given traffic flow. The QoS requirements can be usedto help make mapping decisions. The Mapping Service's interface to thePCRF 126 may be based on the Rx interface that is defined in thereference 3GPP TS 29.211, Rx Interface and Rx/Gx Signaling Flows.Alternatively, the Mapping Service may communicate with the PCRF 126 viaan interface with the SCEF. The SCEF may support an Rx interface withthe PCRF 126.

When the UE 104 or MME 120 decides that the UE 104 should no longermaintain the local PDN connection 306, the MME 120 notifies the mappingservice 302 so that the Mapping Service 302 knows that it should nolonger redirect the UE 104 to local content. The existing UE 104 or MME120 requested PDN disconnection procedure is used to end the PDNconnection 306.

It is understood that the entities performing the steps illustrated inFIG. 6 are logical entities that may be implemented in the form ofsoftware (i.e., computer-executable instructions) stored in a memory of,and executing on a processor of, a network node or computer system suchas those illustrated in FIG. 11 or FIG. 12. That is, the method(s)illustrated in FIG. 6 may be implemented in the form of software (i.e.,computer-executable instructions) stored in a memory of a network node,such as the node or computer system illustrated in FIG. 11 or FIG. 12,which computer executable instructions, when executed by a processor ofthe node, perform the steps illustrated in FIG. 6. It is also understoodthat any transmitting and receiving steps illustrated in FIG. 6 may beperformed by communication circuitry of the node under control of theprocessor of the node and the computer-executable instructions (e.g.,software) that it executes.

FIG. 7 is a diagram that illustrates ending a PDN connection 306 when aUE 104 moves to an SC-AP (not shown) that does not have access to aL-GW.

In step 1 of FIG. 7, a decision is made to disconnect the PDN connection306 that is used to access the local cache at the edge server 308. TheUE 104 or MME 120 decides that the UE should no longer maintain thelocal PDN connection 306. This decision may be triggered by a TAU thatindicates that the UE 104 is, or may be, moving to a cell that cannotaccess the local GW 130. Alternatively, the Mapping Service 302 maydecide, or recommend, to the MME 120 that the UE 104 disconnect thelocal PDN connection. The Mapping Service 302 may decide to do thisbecause the UE 104 has not recently been redirected to the local networkand thus has not recently made use of the cache.

In step 2 of FIG. 7, the MME 120 indicates to the Mapping Service 302that the UE 104 no longer has access to the local network. Thisindication is sent to the Mapping Service 302 by the MME 120 via a newmessage, SUBSCRIBER LOCAL ACCESS NOTIFICATION, on a new interface. Thenew interface is between the MME 120 and Mapping Service 302. This newmessage may carry the following information:

-   -   Subscription Identifier, i.e. IMSI    -   APN Name/PDN Connection ID—The name of the APN or PDN        Connection.    -   L-GW Address or LHN-ID—The L-GW or LHN that the UE disconnected        from.    -   The message may include the IP address(es) of the edge server(s)        that the UE will no longer have access to.

In step 3 of FIG. 7, the Mapping service 302 responds to the MME 120with an acknowledgement, via the SUBSCRIBER LOCAL ACCESS RESPONSEmessage.

In step 4 of FIG. 7, the “UE or MME Initiated PDN DisconnectionProcedure” is executed as described in in section 5.10.3 of reference3GPP TS 23.401 to establish this connection.

Exemplary embodiments can include APN Configuration Changes. During the“E-UTRAN Initial Attach” procedure, the MME 120 sends the HSS 122 an“Update Location Request” message and the HSS 122 responds with an“Update Location Answer” message. “Update Location Answer” message isused to send the UE's subscription information to the MME 120. Thisexchange occurs on the S6a interface. (A similar exchange occurs inUTRAN between the SGSN and HSS on the S6d interface.) “Update LocationAnswer” includes the APN-Configuration Attribute—Value Pair (AVP). ThisAVP describes the permitted configuration for each of the UE'ssubscribed APN's and is defined in 3GPP TS 29.272 section 7.3.35. ThisAVP is enhanced to support the case where the UE 104 is able to accesscached content from an edge server 308 on a local network 128.

For each APN that could have data cached in a local network, theAPN-Configuration AVP can carry the following information:

-   -   Cached-Access-Permitted. This flag indicates to the MME 120        that, when the UE 104 is connected to this APN, the MME 120        should look for opportunities to direct the UE 104 to connect to        a local network that provides cache services to this APN.    -   SIPTO-Local-Network-Permission. This existing AVP can currently        take one of two values; “SIPTO at Local Network ALLOWED” and        “SIPTO at Local Network NOTALLOWED”. It is proposed that this        AVP be allowed to take on a new value called “SIPTO at Local        Network CACHED CONTENT ONLY”. This value is used to indicate        that a SIPTO@LN PDN connection is not allowed to be used for PDN        connection. However, a SIPTO@LN PDN connection could be used        simultaneously with this PDN connection to retrieve cached        content.    -   L-GW Address(es), LHN-ID(s), or Tracking Area Identity (TAI)        Lists that provide access to the cached content.

When the mapping service issues a redirect response, the P-GW 116 mayuse packet filters, e.g. based on IP source address, IP destinationaddress, source port number, destination port number, etc., to detectthat the response is from the mapping service. The P-GW 116 may beconfigured to not charge the UE 104 for this traffic. In other words,the redirect response might not be included in any downlink bit countthat is tallied and send to the Online Charging System (OCS).

As described above, the mapping service 302 can be an HTTP proxy thatcan redirect the UE 104. Alternatively, the mapping service 302 could bepart of the DNS Server. When the UE 104 performs a DNS lookup, theresponse can be based on whether or not the UE 104 has access to localcache servers. If the UE 104 is looking up a URL that is represented inthe local cache, the DNS Server can respond to the UE 104 and redirectit to the local cache.

In this embodiment, the DNS record resolves to two IP address (e.g. oneaddress in the local network and one address in the original contentserver). The mapping service (DNS Server) determines which IP addressshould be used to resolve the URL based on whether or not the requestorhas access to the edge servers. The procedure where the mapping service(DNS Server) is notified that the requestor has access to the edgeserver is shown in FIG. 4.

Whether the mapping service 302 is implemented as an HTTP proxy or a DNSserver, it can be implemented as a 3GPP Application Function (AF) orApplication Server (AS) or TDF with an Rx or Sd interface to the PCRF,an Mh interface to the HSS, and an interface with the MME 120 and/orP-GW 116.

In the architecture of FIG. 3, there are scenarios where a UE 104 coulddownload a web page from the edge servers that includes URLs that linkto other web pages. Accessing the links may cause the UE 104 to send arequest for content to an original content server on the internet. Ifthe requested content also lives in the local network, then the mappingservice may again redirect the UE 104 to cached content. The fact thatall original requests for content are routed through the MCN 102 and theMapping Server 302 is advantageous in the sense that it allows the MCN102 to record all activity and to enforce user restrictions. However,MCN 102 traffic could be further reduced if the local network was ableto modify cached content so that URLs could point to local content.

It is understood that the entities performing the steps illustrated inFIG. 7 are logical entities that may be implemented in the form ofsoftware (i.e., computer-executable instructions) stored in a memory of,and executing on a processor of, a network node or computer system suchas those illustrated in FIG. 11 or FIG. 12. That is, the method(s)illustrated in FIG. 7 may be implemented in the form of software (i.e.,computer-executable instructions) stored in a memory of a network node,such as the node or computer system illustrated in FIG. 11 or FIG. 12,which computer executable instructions, when executed by a processor ofthe node, perform the steps illustrated in FIG. 7. It is also understoodthat any transmitting and receiving steps illustrated in FIG. 4 may beperformed by communication circuitry of the node under control of theprocessor of the node and the computer-executable instructions (e.g.,software) that it executes.

FIG. 8 is a diagram that illustrates an embodiment with a MappingService 302 located in the Mobile Core Network 102 after the P-GW 116and an additional optional local mapping service 802 is located in thelocal network 128.

The purpose of the mapping service 302 in the MCN 102 is to map UErequests for content and to redirect the UE 104 accordingly. However, alocal mapping service 802 could also be provided in the local networkfor remapping URLs that are provided to the UE 104. For example,consider the case where a UE 104 downloads a web page from a local edgeserver 308. The web page may include URLs that point to IP addressesthat are in the Internet. However, the content that is pointed to by theURLs may also live in the edge servers 308. When this is the case, thelocal mapping service may be allowed to modify URLs that are provided toUE 104 so that they map to the cached content in the local network 128.

Note that this local mapping service 802 may be required to access userrelated policies, such as parental controls, so that the user isprevented from being redirected to content that is not permitted.

It is understood that the functionality illustrated in FIG. 8, may beimplemented in the form of software (i.e., computer-executableinstructions) stored in a memory of, and executing on a processor of, anode of an M2M network (e.g., a server, gateway, device, or othercomputer system), such as one of those illustrated in FIG. 11 or 12described below.

FIG. 9 is a diagram that illustrates an embodiment with a MappingService 302 located in the Mobile Core Network 102 after the P-GW and aspecial PDN 902 that holds the edge servers 904. The edge servers 904are physically close to the P-GWs 116 and 906 that provide access to thePDN's 118 and 902.

A UE 104 may have a first PDN connection to the “internet” PDN 118.Although the content that the UE 104 access resides in the “internet”PDN 118, it may be very far from the UE 104. Depending on InternetService Provider (ISP) peering agreements, the content may need totraverse many networks before reaching the MNO's P-GW 116. Thus, itmight not be possible for the user to obtain a low latency connection.

A UE 104 may maintain a second PDN connection to the MNO Operated PDN902 that includes the edge servers 904. When the UE 104 maintains bothPDN connections, the mapping service 302 that is associated with thefirst PDN connection may redirect the UE 104 to the cached content thatis stored in edge server 904 of PDN 902.

A deep-packet inspection function such as the mapping service 302, or atraffic detection function, may detect or anticipate that the UE 104 isgoing to accessing data that is available in the MNO's edge servers 904.Based on the UE's capabilities and the subscriber's permissions, adecision may be made to command, or request, that the UE 104 establish asecond PDN connection. The second PDN connection gives the UE 104 accessto the edge servers 904.

Steps 2 and 3 of the call flow of FIG. 5 show the MME sending a new PDNSERVICES ADVERTISEMENT REQ message to the UE and the UE responding tothe MME with a new PDN SERVICES ADVERTISEMENT RESP message. For FIG. 5,it was proposed that the MME 120 originate this message because thedecision to establish the second PDN connection was based largely on theUE's location and the availability of edge servers in the small cellnetwork. In the embodiment of FIG. 9, the decision to establish thesecond PDN connection is based largely on the result of deep packetinspection that is performed on the output of the P-GW function. Thus,in this section, it is proposed that the P-GW 116 be allowed to send anew PDN SERVICES ADVERTISEMENT REQ message to the UE 104 (via the MME120 or S-GW 114) and the UE 104 may respond to the P-GW 116 (via the MME120 or S-GW 114) with a new PDN SERVICES ADVERTISEMENT RESP message. ThePDN SERVICES ADVERTISEMENT REQ message from the P-GW 116 indicates theAPN that can be used to access the Edge Servers 904 to the UE 104. Thisnew message can be considered a NAS mobility management message. TheP-GW 116 may know to send the PDN SERVICES ADVERTISEMENT REQ messagebased on a message from the Mapping Service 302. The Mapping Service 302may send the message to the P-GW via an SCEF.

Steps 5 and 6 of the call flow of FIG. 4 show the MME 120 sending a newSUBSCRIBER LOCAL ACCESS NOTIFICATION message to the Mapping Service andthe Mapping Service Responding to the MME 120 with a SUBSCRIBER LOCALACCESS RESPONSE message. In section 5.1.2, it was proposed that the MME120 originate this message because it was the entity that coordinatedthe establishment of the second PDN connection. Thus, in thisembodiment, it is proposed that the P-GW 116 (via the MME 120 or S-GW114) be allowed to send a new LOCAL ACCESS NOTIFICATION message to theMapping Service 302 and the Mapping Service 302 may respond to the P-GW116 (via the MME 120 or S-GW 114) with a new PDN SUBSCRIBER LOCAL ACCESSRESPONSE message.

By placing the edge servers 904 in a second PDN 902 that is separatefrom the first PDN 118, the MNO can architect their MCN 102 such thatinternet traffic and high volume downloads from the edge servers 904 donot compete for the same MCN resources. For example, the PDN's 118 and902 do not need to compete for the same P-GW resources.

Compared to the architecture of FIG. 3, the architecture of FIG. 9 hasthe advantage that the MCN 102 has complete visibility of all UEtraffic. Thus, since all traffic traverses the MCN 102, the charginginfrastructure of the UE 104 can be completely utilized.

It is understood that the entities performing the steps illustrated inFIG. 9 are logical entities that may be implemented in the form ofsoftware (i.e., computer-executable instructions) stored in a memory of,and executing on a processor of, a network node or computer system suchas those illustrated in FIG. 11 or FIG. 12. That is, the method(s)illustrated in FIG. 9 may be implemented in the form of software (i.e.,computer-executable instructions) stored in a memory of a network node,such as the node or computer system illustrated in FIG. 11 or FIG. 12,which computer executable instructions, when executed by a processor ofthe node, perform the steps illustrated in FIG. 9. It is also understoodthat any transmitting and receiving steps illustrated in FIG. 4 may beperformed by communication circuitry of the node under control of theprocessor of the node and the computer-executable instructions (e.g.,software) that it executes.

Interfaces, such as Graphical User Interfaces (GUIs), can be used toassist user to control and/or configure functionalities related to thelocal content redirection. FIG. 10 is a diagram that illustrates aninterface 1002 that allows a user to display data 1004, and update data1006. For example, the data mentioned above with respect to step 4 ofFIG. 4 (URL of the original content 314; URL of the cached content andthe local IP Address of the Edge Server; The name of the local devicewhere the content is cached; and Name of the APN(s) that is associatedwith this content) can be accessed and updated using GUI 1002. The GUI1002 can allow for searching for such data as well. GUI 1008 can be usedto allow a user at a UE to select whether to allow local contentredirection, such as during step 2 of FIG. 4.

It is to be understood that interface 1002 and other such interfaces canbe produced using displays such as those shown in FIGS. 11 and 12described below.

FIG. 11 is a diagram of an example node 30 such as a UE (e.g., UEs 104and 210 in FIGS. 1-3 and 5-9) or other end node device. The end node 30can be used to implement any of the elements disclosed in thisspecification including User Equipment 104.

The node 30 can execute or include logical entities such as the mappingservice 302, logical entities at the user equipment 104, data collectionand analytics 314, edge servers 308 and 904, SC-AP 106, L-GW 130, SeGW108, SC-GW 112, S-GW 114, P-GW 116, HSS 122, MME 120, PCRF 126,management portal 310, and local mapping service 802 and the logicalentities for graphical interfaces such as graphical user interfaces 1002and 1008. The device 30 can be part of an M2M network or part of anon-M2M network. As shown in FIG. 11, the End node 30 may include aprocessor 32, non-removable memory 44, removable memory 46, aspeaker/microphone 38, a keypad 40, a display, touchpad, and/orindicators 42, a power source 48, a global positioning system (GPS)chipset 50, and other peripherals 52. The node 30 may also includecommunication circuitry, such as a transceiver 34 and a transmit/receiveelement 36. It will be appreciated that the Node 30 may include anysub-combination of the foregoing elements while remaining consistentwith an embodiment. This node may be a node that implements the SMSFfunctionality described herein.

The processor 32 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Array (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. In general, the processor 32 may executecomputer-executable instructions stored in the memory (e.g., memory 44and/or memory 46) of the node in order to perform the various requiredfunctions of the node. For example, the processor 32 may perform signalcoding, data processing, power control, input/output processing, and/orany other functionality that enables the End node 30 to operate in awireless or wired environment. The processor 32 may runapplication-layer programs (e.g., browsers) and/or radio access-layer(RAN) programs and/or other communications programs. The processor 32may also perform security operations such as authentication, securitykey agreement, and/or cryptographic operations, such as at theaccess-layer and/or application layer for example.

As shown in FIG. 11, the processor 32 is coupled to its communicationcircuitry (e.g., transceiver 34 and transmit/receive element 36). Theprocessor 32, through the execution of computer executable instructions,may control the communication circuitry in order to cause the node 30 tocommunicate with other nodes via the network to which it is connected.In particular, the processor 32 may control the communication circuitryin order to perform the transmitting and receiving steps describedherein and in the claims. While FIG. 11 depicts the processor 32 and thetransceiver 34 as separate components, it will be appreciated that theprocessor 32 and the transceiver 34 may be integrated together in anelectronic package or chip.

The transmit/receive element 36 may be configured to transmit signalsto, or receive signals from, other Nodes, including M2M servers,gateways, device, and the like. For example, in an embodiment, thetransmit/receive element 36 may be an antenna configured to transmitand/or receive RF signals. The transmit/receive element 36 may supportvarious networks and air interfaces, such as WLAN, WPAN, cellular, andthe like. In an embodiment, the transmit/receive element 36 may be anemitter/detector configured to transmit and/or receive IR, UV, orvisible light signals, for example. In yet another embodiment, thetransmit/receive element 36 may be configured to transmit and receiveboth RF and light signals. It will be appreciated that thetransmit/receive element 36 may be configured to transmit and/or receiveany combination of wireless or wired signals.

In addition, although the transmit/receive element 36 is depicted inFIG. 11 as a single element, the Node 30 may include any number oftransmit/receive elements 36. More specifically, the Node 30 may employMIMO technology. Thus, in an embodiment, the Node 30 may include two ormore transmit/receive elements 36 (e.g., multiple antennas) fortransmitting and receiving wireless signals.

The transceiver 34 may be configured to modulate the signals that are tobe transmitted by the transmit/receive element 36 and to demodulate thesignals that are received by the transmit/receive element 36. As notedabove, the Node 30 may have multi-mode capabilities. Thus, thetransceiver 34 may include multiple transceivers for enabling the Node30 to communicate via multiple RATs, such as UTRA and IEEE 802.11, forexample.

The processor 32 may access information from, and store data in, anytype of suitable memory, such as the non-removable memory 44 and/or theremovable memory 46. For example, the processor 32 may store sessioncontext in its memory, as described above. The non-removable memory 44may include random-access memory (RAM), read-only memory (ROM), a harddisk, or any other type of memory storage device. The removable memory46 may include a subscriber identity module (SIM) card, a memory stick,a secure digital (SD) memory card, and the like. In other embodiments,the processor 32 may access information from, and store data in, memorythat is not physically located on the Node 30, such as on a server or ahome computer. The processor 32 may be configured to control lightingpatterns, images, or colors on the display or indicators 42 to reflectthe status of an M2M service layer session migration or sharing or toobtain input from a user or display information to a user about thenode's session migration or sharing capabilities or settings. In anotherexample, the display may show information with regard to a sessionstate. The current disclosure defines a RESTful user/application API inthe oneM2M embodiment. A graphical user interface, which may be shown onthe display, may be layered on top of the API to allow a user tointeractively establish and manage an E2E session, or the migration orsharing thereof, via the underlying service layer session functionalitydescribed herein.

The processor 32 may receive power from the power source 48, and may beconfigured to distribute and/or control the power to the othercomponents in the Node 30. The power source 48 may be any suitabledevice for powering the Node 30. For example, the power source 48 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 32 may also be coupled to the GPS chipset 50, which isconfigured to provide location information (e.g., longitude andlatitude) regarding the current location of the Node 30. It will beappreciated that the Node 30 may acquire location information by way ofany suitable location-determination method while remaining consistentwith an embodiment.

The processor 32 may further be coupled to other peripherals 52, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 52 may include anaccelerometer, an e-compass, a satellite transceiver, a sensor, adigital camera (for photographs or video), a universal serial bus (USB)port, a vibration device, a television transceiver, a hands freeheadset, a Bluetooth® module, a frequency modulated (FM) radio unit, adigital music player, a media player, a video game player module, anInternet browser, and the like.

FIG. 12 is a block diagram of an exemplary computing system 90 which mayalso be used to implement one or more nodes of an M2M network, such asan M2M server, gateway, device, or other node. Computing system 90 maycomprise a computer or server and may be controlled primarily bycomputer readable instructions, which may be in the form of software,wherever, or by whatever means such software is stored or accessed.Computing system 90 can execute or include logical entities such as themapping service 302, logical entities at the user equipment 104, datacollection and analytics 314, edge servers 308 and 904, SC-AP 106, L-GW130, SeGW 108, SC-GW 112, S-GW 114, P-GW 116, HSS 122, MME 120, PCRF126, management portal 310, and local mapping service 802 and thelogical entities for graphical interfaces such as graphical userinterfaces 1002 and 1008. Computing system 90 can be an M2M device, userequipment, gateway, UE/GW or any other nodes including nodes of themobile care network, service layer network application provider,terminal device 18 or an M2M gateway device 14 for example. Suchcomputer readable instructions may be executed within a processor, suchas central processing unit (CPU) 91, to cause computing system 90 to dowork. In many known workstations, servers, and personal computers,central processing unit 91 is implemented by a single-chip CPU called amicroprocessor. In other machines, the central processing unit 91 maycomprise multiple processors. Coprocessor 81 is an optional processor,distinct from main CPU 91, that performs additional functions or assistsCPU 91. CPU 91 and/or coprocessor 81 may receive, generate, and processdata related to the disclosed systems and methods for E2E M2M servicelayer sessions, such as receiving session credentials or authenticatingbased on session credentials.

In operation, CPU 91 fetches, decodes, and executes instructions, andtransfers information to and from other resources via the computer'smain data-transfer path, system bus 80. Such a system bus connects thecomponents in computing system 90 and defines the medium for dataexchange. System bus 80 typically includes data lines for sending data,address lines for sending addresses, and control lines for sendinginterrupts and for operating the system bus. An example of such a systembus 80 is the PCI (Peripheral Component Interconnect) bus.

Memories coupled to system bus 80 include random access memory (RAM) 82and read only memory (ROM) 93. Such memories include circuitry thatallows information to be stored and retrieved. ROMs 93 generally containstored data that cannot easily be modified. Data stored in RAM 82 can beread or changed by CPU 91 or other hardware devices. Access to RAM 82and/or ROM 93 may be controlled by memory controller 92. Memorycontroller 92 may provide an address translation function thattranslates virtual addresses into physical addresses as instructions areexecuted. Memory controller 92 may also provide a memory protectionfunction that isolates processes within the system and isolates systemprocesses from user processes. Thus, a program running in a first modecan access only memory mapped by its own process virtual address space;it cannot access memory within another process's virtual address spaceunless memory sharing between the processes has been set up.

In addition, computing system 90 may contain peripherals controller 83responsible for communicating instructions from CPU 91 to peripherals,such as printer 94, keyboard 84, mouse 95, and disk drive 85.

Display 86, which is controlled by display controller 96, is used todisplay visual output generated by computing system 90. Such visualoutput may include text, graphics, animated graphics, and video. Display86 may be implemented with a CRT-based video display, an LCD-basedflat-panel display, gas plasma-based flat-panel display, or atouch-panel. Display controller 96 includes electronic componentsrequired to generate a video signal that is sent to display 86.

Further, computing system 90 may contain communication circuitry, suchas for example a network adaptor 97, that may be used to connectcomputing system 90 to an external communications network, to enable thecomputing system 90 to communicate with other nodes of the network.

It is understood that any or all of the systems, methods, and processesdescribed herein may be embodied in the form of computer executableinstructions (i.e., program code) stored on a computer-readable storagemedium which instructions, when executed by a machine, such as a node ofan M2M network, including for example an M2M server, gateway, device orthe like, perform and/or implement the systems, methods and processesdescribed herein. Specifically, any of the steps, operations orfunctions described above, including the operations of the gateway, UE,UE/GW, or any of the nodes of the mobile core network, service layer ornetwork application provider, may be implemented in the form of suchcomputer executable instructions. Logical entities such as the mappingservice 302, logical entities at the user equipment 104, data collectionand analytics 314, edge servers 308 and 904, SC-AP 106, L-GW 130, SeGW108, SC-GW 112, S-GW 114, P-GW 116, HSS 122, MME 120, PCRF 126,management portal 310, and local mapping service 802 and the logicalentities for graphical interfaces such as graphical user interfaces 1002and 1008 may be embodied in the form of the computer executableinstructions stored on a computer-readable storage medium. Computerreadable storage media include both volatile and nonvolatile, removableand non-removable media implemented in any non-transitory (i.e.,tangible or physical) method or technology for storage of information,but such computer readable storage media do not includes signals.Computer readable storage media include, but are not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other tangible or physical medium which can be used to store thedesired information and which can be accessed by a computer.

In describing preferred embodiments of the subject matter of the presentdisclosure, as illustrated in the Figures, specific terminology isemployed for the sake of clarity. The claimed subject matter, however,is not intended to be limited to the specific terminology so selected,and it is to be understood that each specific element includes alltechnical equivalents that operate in a similar manner to accomplish asimilar purpose.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have elements that do notdiffer from the literal language of the claims, or if they includeequivalent elements with insubstantial differences from the literallanguage of the claims.

What is claimed:
 1. A method for a user plane interaction, the methodcomprising: connecting with a first packet data network using a firstpacket data network connection; sending a content request on the firstpacket data network connection; in response to sending the contentrequest on the first packet data network connection, receiving a messagecomprising information for the user equipment to access data from asecond packet data network, wherein the mobile core network generatesthe message based on the content request from the user equipment afterthe content request has reached an anchor of the first packet datanetwork connection; accessing, using the information and a second packetdata network connection, data from the second packet data network; andreceiving a packet data network service advertisement request messageand the message includes an access point name, wherein the packet datanetwork service advertisement request message comprises an indication ofone or more of: a security header type, a services advertisement type,or a packet data network type.
 2. The method of claim 1, wherein: theinformation comprising at least a URL or an IP Address, or the contentrequest is an HTTP content request.
 3. The method of claim 1, whereinthe data request is associated with a domain name system lookup.
 4. Themethod of claim 1, wherein the anchor of the first packet data networkconnection comprises a packet data network gateway.
 5. The method ofclaim 1, wherein the data request is associated with a hypertexttransfer protocol request.
 6. The method of claim 1, wherein the mobilecore network determines, based at least on a location of the userequipment and a deep packet inspection of a data request from the userequipment, that the user equipment should connect to the second packetdata network using the second packet data network connection in order toaccess the data.
 7. A user equipment in communication with first packetdata network using a first packet data network connection, the userequipment comprising a processor and a memory, the memory storingcomputer-executable instructions which, when executed by the processor,cause the user equipment to perform operations comprising: sending acontent request on the first packet data network connection; in responseto sending the content request on the first packet data networkconnection, receiving a message comprising information for the userequipment to access data from a second packet data network, wherein amobile core network generates the message based on the content requestfrom the user equipment after the content request has reached an anchorof the first packet data network connection; accessing, using theinformation and a second packet data network connection, data from thesecond packet data network; and receiving a packet data network serviceadvertisement request message and the message includes an access pointname, wherein the packet data network service advertisement requestmessage comprises an indication of one or more of: a security headertype, a services advertisement type, or a packet data network type. 8.The user equipment of claim 7, further comprising receiving a packetdata network service advertisement request message and the messageincludes an access point name.
 9. The user equipment of claim 8, whereinthe content request is an HTTP content request.
 10. The user equipmentof claim 7, wherein the information comprises an internet protocoladdress.
 11. The user equipment of claim 7, wherein the data request isassociated with a hypertext transfer protocol request or domain namesystem lookup.
 12. The user equipment of claim 7, wherein the mobilecore network determines, based at least on a location of the userequipment and a deep packet inspection of a data request from the userequipment, that the user equipment should connect to the second packetdata network using the second packet data network connection in order toaccess the data.
 13. A computer-readable storage medium storingcomputer-executable instructions which, when executed by a processor ofa user equipment in communication with first packet data network using afirst packet data network connection, cause the user equipment toperform operations comprising: sending a content request on the firstpacket data network connection; in response to sending the contentrequest on the first packet data network connection, receiving a messagecomprising information for the user equipment to access data from asecond packet data network, wherein the mobile core network generatesthe message based on the content request from the user equipment afterthe content request has reached an anchor of the first packet datanetwork connection; accessing, using the information and a second packetdata network connection, data from the second packet data network; andreceiving a packet data network service advertisement request messageand the message includes an access point name, wherein the packet datanetwork service advertisement request message comprises an indication ofone or more of: a security header type, a services advertisement type,or a packet data network type.
 14. The computer-readable storage mediumof claim 13, wherein the content request is an HTTP content request. 15.The computer-readable storage medium of claim 13, wherein the datarequest is associated with a domain name system lookup.
 16. Thecomputer-readable storage medium of claim 13, wherein the data requestis associated with a hypertext transfer protocol request.
 17. Thecomputer-readable storage medium of claim 13, wherein the mobile corenetwork determines, based at least on a location of the user equipmentand a deep packet inspection of a data request from the user equipment,that the user equipment should connect to the second packet data networkusing the second packet data network connection in order to access thedata.
 18. The computer-readable storage medium of claim 13, wherein theanchor of the first packet data network connection comprises a packetdata network gateway.